String parsing analyzer to replace regex split, enables ^CC and ^CT commands #189
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ZPL ^FD commands sometimes come with ^ and ~ characters in the data. This breaks the parser which sees unrecognized commands. The way these are stored is by swapping out the caret(CC) or tilde(CT) characters with an unused one momentarily before reading the FD data, then swapping back the original symbol(s) after.
This still returns an array of strings like the old
SplitZplCommands
signature.We patch back the commands with the default caret and tilde so that the command analyzers do not have to be modified.
The capacity sizes for the buffers are arbitrary, but what I'd consider a reasonable amount for shipping labels.
Ideally, there would be work to support the ^
CSCD command as well, but because most command analyzers rely on splitting on commas, there are architectural discussions to be had prior.